Apparatus, system and method of offloading traffic of a secondary cell group (scg)

ABSTRACT

Some demonstrative embodiments include devices, systems and methods of offloading traffic of a Secondary Cell Group (SCG). For example, some embodiments may include identifying a SCG bearer that is offloadable to the Internet via a Network Address Translation (NAT) gateway, based on offloading information received from a Master Evolved Node B (eNB) (MeNB); and offloading uplink Internet Protocol (IP) packets of the SCG bearer to the Internet via the NAT gateway, if the SCG bearer is indicated to be offloadable.

CROSS REFERENCE

This Application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/130,991 entitled “Selective IPTraffic Offload With Dual Connectivity”, filed Mar. 10, 2015, the entiredisclosure of which is incorporated herein by reference.

TECHNICAL FIELD

Some embodiments described herein generally relate to offloading trafficof a Secondary Cell Group (SCG).

BACKGROUND

A Dual-Connectivity scheme may be configured to enable a User Equipment(UE) to consume radio resources provided by two different network nodes,for example, a Master Evolved Node B (eNB) (MeNB) and a Secondary eNB(SeNB).

The MeNB may be an eNB, which may serve as an anchor towards a CoreNetwork (CN), for example, via a connection with a Mobility ManagementEntity (MME), e.g., via an S1-MME interface. The MeNB may be connectedto a plurality of SeNBs, which may be able to provide additional radioresources to the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of elements of a node, in accordancewith some demonstrative embodiments.

FIG. 3 is a schematic illustration of a system including a NetworkAddress Translation (NAT) gateway to offload traffic from at least oneSecondary Evolved Node B (SeNB), in accordance with some demonstrativeembodiments.

FIG. 4 is a schematic illustration of a system including a NAT gatewaycollocated with a SeNB, in accordance with some demonstrativeembodiments.

FIG. 5 is a schematic illustration of a system including a NAT gatewayto intercept and offload traffic of a SeNB, in accordance with somedemonstrative embodiments.

FIG. 6 is a schematic illustration of elements of a NAT gateway, inaccordance with some demonstrative embodiments.

FIG. 7 is a schematic flow-chart illustration of a method of offloadingtraffic of a Secondary Cell Group (SCG), in accordance with somedemonstrative embodiments.

FIG. 8 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment,” “an embodiment,” “demonstrativeembodiment,” “various embodiments,” etc., indicate that theembodiment(s) so described may include a particular feature, structure,or characteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a Smartphone device, a server computer, a handheld computer, ahandheld device, a Personal Digital Assistant (PDA) device, a handheldPDA device, an on-board device, an off-board device, a hybrid device, avehicular device, a non-vehicular device, a mobile or portable device, aconsumer device, a non-mobile or non-portable device, a wirelesscommunication station, a wireless communication device, a wirelessAccess Point (AP), a wireless node, a cellular node, a relay node, abase station (BS), a wired or wireless router, a wired or wirelessmodem, a video device, an audio device, an audio-video (A/V) device, awired or wireless network, a wireless area network, a cellular network,a cellular node, a cellular device, a Wireless Local Area Network(WLAN), a Multiple Input Multiple Output (MIMO) transceiver or device, aSingle Input Multiple Output (SIMO) transceiver or device, a MultipleInput Single Output (MISO) transceiver or device, a device having one ormore internal antennas and/or external antennas, Digital Video Broadcast(DVB) devices or systems, multi-standard radio devices or systems, awired or wireless handheld device, e.g., a Smartphone, a WirelessApplication Protocol (WAP) device, vending machines, sell terminals, andthe like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Long Term Evolution (LTE)specifications (including 3GPP TS 36.300 (3GPP TS 36.300 V11.7.0(2013-09); Technical Specification; 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved UniversalTerrestrial Radio Access (E-UTRA) and Evolved Universal TerrestrialRadio Access Network (E-UTRAN); Overall description; Stage 2 (Release11)); and/or 3GPP TS 36.413 (ETSI TS 136 413 V12.4.0 (2015-02) LTE;Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1Application Protocol (S1AP) (3GPP TS 36.413 version 12.4.0 Release12))), and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing IEEE 802.16 standards(IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed BroadbandWireless Access Systems; IEEE-Std 802.16e, 2005 Edition, Physical andMedium Access Control Layers for Combined Fixed and Mobile Operation inLicensed Bands; amendment to IEEE Std 802.16-2009, developed by TaskGroup m) and/or future versions and/or derivatives thereof, devicesand/or networks operating in accordance with existing IEEE 802.11standards (IEEE 802.11-2012, IEEE Standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks—Specific requirements Part 11:Wireless IAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications, Mar. 29, 2012; IEEE 802.11ad (“IEEE P802.11ad-2012, IEEEStandard for Information Technology—Telecommunications and InformationExchange Between Systems—Local and Metropolitan Area Networks—SpecificRequirements—Part 11: Wireless LAN Medium Access Control (MAC) andPhysical Layer (PHY) Specifications—Amendment 3: Enhancements for VeryHigh Throughput in the 60 GHz Band”, 28 December, 2012)) and/or futureversions and/or derivatives thereof, units and/or devices which are partof the above networks, and the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM(OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA),Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA),Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extendedGPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation(MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System(GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB),Global System for Mobile communication (GSM), second generation (2G),2.5G, 3G, 3.5G, 4G, 4.5G, Fifth Generation (5G) mobile networks, 3GPP,Long Term Evolution (LTE) cellular system, LTE advance cellular system,LTE Unlicensed systems, High-Speed Downlink Packet Access (HSDPA),High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access(HSPA), HSPA+, Single Carrier Radio Transmission Technology (1×RTT),Evolution-Data Optimized (EV-DO), Enhanced Data rates for GSM Evolution(EDGE), and the like. Other embodiments may be used in various otherdevices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a wirelesscommunication signal includes transmitting the wireless communicationsignal and/or receiving the wireless communication signal. For example,a wireless communication unit, which is capable of communicating awireless communication signal, may include a wireless transmitter totransmit the wireless communication signal to at least one otherwireless communication unit, and/or a wireless communication receiver toreceive the wireless communication signal from at least one otherwireless communication unit. The verb “communicating” may be used torefer to the action of transmitting or the action of receiving. In oneexample, the phrase “communicating a signal” may refer to the action oftransmitting the signal by a first device, and may not necessarilyinclude the action of receiving the signal by a second device. Inanother example, the phrase “communicating a signal” may refer to theaction of receiving the signal by a first device, and may notnecessarily include the action of transmitting the signal by a seconddevice.

As used herein, the term “circuitry” may refer to, be part of, orinclude, an Application Specific Integrated Circuit (ASIC), anintegrated circuit, an electronic circuit, a processor (shared,dedicated, or group), and/or memory (shared, dedicated, or group), thatexecute one or more software or firmware programs, a combinational logiccircuit, and/or other suitable hardware components that provide thedescribed functionality. In some embodiments, the circuitry may beimplemented in, or functions associated with the circuitry may beimplemented by, one or more software or firmware modules. In someembodiments, circuitry may include logic, at least partially operable inhardware.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a dipole antenna, a set of switched beamantennas, and/or the like.

The term “cell”, as used herein, may include a combination of networkresources, for example, downlink and optionally uplink resources. Theresources may be controlled and/or allocated, for example, by a node(also referred to as a “base station”), or the like. The linking betweena carrier frequency of the downlink resources and a carrier frequency ofthe uplink resources may be indicated in system information transmittedon the downlink resources.

Some demonstrative embodiments are described herein with respect to aLTE network. However, other embodiments may be implemented in any othersuitable cellular network or system, e.g., a Universal MobileTelecommunications System (UMTS) cellular system, a GSM network, a 3Gcellular network, a 4G cellular network, a 4.5G network, a 5G cellularnetwork, a WiMAX cellular network, and the like.

Some demonstrative embodiments may be used in conjunction with aHeterogeneous Network (HetNet), which may utilize a deployment of a mixof technologies, frequencies, cell sizes and/or network architectures,e.g., including cellular, millimeter wave (“mmWave” or “mmW”), and/orthe like. In one example, the HetNet may include a radio access networkhaving layers of different-sized cells ranging from large macrocells tosmall cells, for example, picocells and femtocells. Other embodimentsmay be used in conjunction with any other suitable wirelesscommunication network.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100, in accordance with some demonstrativeembodiments. In one example, cellular system 100 may include a 4thgeneration cellular system such as, for example, a long-term evolution(LTE) or LTE advance cellular system, and the like, or a 5G cellularsystem. In other embodiments, system 100 may include any other cellularsystem.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude a plurality of nodes, e.g., including nodes 102, 104 and/or 106,capable of communicating content, data, information and/or signals withone or more User Equipment (UE) 119, e.g., as described below.

In some demonstrative embodiments, nodes 102, 104 and/or 106 may beconfigured to operate as eNBs and/or to provide one or morefunctionalities of an eNB, e.g., to one or more UE 119, which may beconnected to nodes 102, 104 and/or 106. For example, nodes 102, 104and/or 106 may be configured to perform radio resource management (RRM),radio bearer control, radio admission control (access control),connection mobility management, resource scheduling between UEs and eNBradios, e.g., Dynamic allocation of resources to UEs in both uplink anddownlink, header compression, link encryption of user data streams,packet routing of user data towards a destination, e.g., another eNB oran Evolved Packet Core (EPC), scheduling and/or transmitting pagingmessages, e.g., incoming calls and/or connection requests, broadcastinformation coordination, measurement reporting, and/or any otheroperations.

In some demonstrative embodiments, system 100 may be configuredaccording to a Dual-Connectivity (DC) scheme, which may be configured toenable UE 119 to consume radio resources provided by two differentnetwork nodes, for example, a Master Evolved Node B (eNB) (MeNB) and aSecondary eNB (SeNB), e.g., as described below.

In some demonstrative embodiments, node 106 may be configured to operateas a MeNB, which may be configured to control a Macro Cell 110 (alsoreferred to as a “Master Cell Group (MCG)”).

In some demonstrative embodiments, MeNB 106 may be configured to serveas an anchor towards a Core Network (CN), for example, via a connectionwith a Mobility Management Entity (MME) 127, e.g., via an S1-MMEinterface 124. For example, MME may be connected to a Serving Gateway(SGW) 130, e.g., via a S11 interface. As shown in FIG. 1, for example,SGW 130 may be connected to a Packet Data Network (PDN) Gateway (PGW)129, e.g., via a S5 interface.

In some demonstrative embodiments, the capacity of the Macro cell 110controlled by MeNB may be enhanced and/or boosted, e.g., in one or moreareas of the cell, by connecting MeNB 106 to a plurality of SeNBs. Forexample, node 102 may be configured to operate as a first SeNB, denotedSeNB-1, and/or node 104 may be configured to operate as a second SeNB,denoted SeNB-2. The SeNB-1 102 may be connected to MeNB 106 via an X2connection 108, and/or the SeNB-2 104 may be connected to MeNB 106 viaan X2 connection 109.

In some demonstrative embodiments, SeNB 102 and/or SeNB 104 may beconfigured to provide additional radio resources to the UE 119. As shownin FIG. 1, SeNBs 102 and 104 may not operate as a MeNB. For example, asshown in FIG. 1, SeNB 102 and SeNB 104 may not terminate an S1-MMEinterface with MME 127.

In some demonstrative embodiments, SeNB 102 and/or SeNB 104 may beconfigured to control a group (also referred to as “Secondary Cell Group(SCG)”) of serving cells. For example, SeNB 102 may communicate with UE119 traffic of a one or more first SCG bearers using radio resources ofSeNB 102, and/or SeNB 104 may communicate with UE 119 traffic of one ormore second SCG bearers using radio resources of SeNB 104, e.g.,according to the dual connectivity scheme.

In some demonstrative embodiments, MeNB 106, SeNB 102, and/or SeNB 104may be connected to SGW 130 by S1-U interfaces 126.

In some demonstrative embodiments, although SeNB 102 and/or SeNB 104 maybe within macro cell 110 under the coverage of MeNB 106, in somescenarios and/or use cases, SeNB 102 and/or SeNB 104 may be deployed inlocations that are outside of a network (also referred to as “MobileNetwork Operator's (MNO's) network”) 193, which may be controlled by theMNO. For example, SeNB 102 and/or SeNB 104 may be deployed as part of alocal network 195, for example, in customer premises, at an office, at ashopping mall, and the like. For example, as shown in FIG. 1, a boundary194 between the MNO's network 193 and the local network 195 may separatebetween MeNB 106 and SeNBs 102 and/or 104.

In some demonstrative embodiments, as shown in FIG. 1, SeNB 102 and/orSeNB 104 may be connected to the MNO network 193, for example, byconnections which may cross the boundary 194, for example, via the X2connections 108 and 109, which may be connected to MeNB 106, and/or viaS1-U interfaces 126, which may be connected to SGW 130.

In some demonstrative embodiments, the X2 connections 108 and/or 109 maybe configured to communicate both Control Plane (C-plane) and User Plane(U-plane) traffic between MeNB 106 and SeNBs 102 and/or 104.

In some demonstrative embodiments, S1-U interfaces 126 may be configuredto communicate U-plane traffic, e.g., between SGW 130 and SeNB 102, SeNB104, and/or MeNB 106.

In some demonstrative embodiments, one or more elements of system 100may be configured to enable Selective IP Traffic Offload (SIPTO) fordual connectivity, for example, to offload traffic communicated betweenUE 119 and the Internet 122, e.g., as described below.

In some demonstrative embodiments, one or more elements of system 100may be configured to support SIPTO at a local network, e.g., localnetwork 195, as described below.

In some demonstrative embodiments, one or more elements of system 100may be configured to enable offloading traffic of a SCG bearer to theInternet 122, e.g., as described below.

In some demonstrative embodiments, it may be advantageous for the MNO tobe able to offload Internet traffic, e.g., all Internet traffic, at aSeNB, for example, instead of having to backhaul the Internet traffic tothe Evolved Packet Core, e.g., if the local network 195 has directaccess to the Internet 122.

In some demonstrative embodiments, one or more elements of system 100may be configured to offload Internet traffic to the Internet 122 atSeNB 102, e.g., via a route 134, which may not need to go through theEPC, for example, instead of backhauling the Internet traffic to the EPCvia a route 136, e.g., via SGW 130.

In some demonstrative embodiments, MeNB 106 may be configured to supportSIPTO at MeNB 106. However, offloading traffic at the MeNB 106 may stillnot enable to perform the traffic offloading at SeNB 102 and/or SeNB104, without going through the backhaul route 136. For example, althoughthe X2 connections 108 and 109 are shown in FIG. 1 as short straightlines between MeNB 106 and the SeNBs 102 and 104, actual transport of X2traffic may involve resource-consuming “hairpins”, e.g., via the MNO'sbackhaul network.

In some demonstrative embodiments, one or more elements of system 100may be configured to perform SIPTO at an SeNB, for example, SeNB 102and/or SeNB 104, e.g., as described below.

In some demonstrative embodiments, a local gateway (L-GW) function maybe collocated with a SeNB. In some scenarios, at time of activation of aSIPTO PDN connection at MME 127, an address of the L-GW collocated withthe SeNB may not yet be available to the MME 127. For example, anactivation of SeNB 102 may occur after activation of a SIPTO PDNconnection at MME 27, e.g., at an E-UTRAN Radio Access Bearer (E-RAB)SETUP REQUEST. According to these embodiments, conventional SIPTOmechanisms may not be able to support dual connectivity with thecollocated L-GW function. Accordingly, the conventional SIPTO mechanismsmay not be able to support offloading of a SCG bearer at SeNB 102 and/orSeNB 104.

In some demonstrative embodiments, system 100 may be configured toimplement an IP traffic mechanism, which may be configured to enableoffloading SCG bearers, for example, directly, from SeNB 102 and/or SeNB104 in dual connectivity, e.g., as described below.

In some demonstrative embodiments, system 100 may be configured tooffload traffic of an SCG bearer to the Internet 122 via at least oneNetwork Address Translation (NAT) gateway 192, e.g., as described below.

In some demonstrative embodiments, SeNB 102 may be configured to receiveinformation (“offload information”), e.g., an offload indication, toindicate which SCG bearers may be offloaded to the Internet 122, e.g.,at SeNB 102; and/or SeNB 104 may be configured to receive offloadinformation, e.g., an offload indication, to indicate which SCG bearersmay be offloaded to the Internet 122, e.g., at SeNB 104.

In some demonstrative embodiments, SeNB 102 and/or SeNB 104 may beconfigured to receive the offload information from the CN, for example,via MeNB 106, for example, since SeNB 102 and/or SeNB 104 may not havean S1-MME connection to MME 127, e.g., as described above.

In some demonstrative embodiments, MeNB 106 may be configured to receivethe offload information corresponding to SeNB 102 and/or SeNB 104 fromMME 127, e.g., via S1-MME connection 124.

In some demonstrative embodiments, MeNB 106 may be configured to receivethe offload information corresponding to SeNB 102 and/or SeNB 104 via anInformation Element (IE) in a [S1-AP] E-RAB SETUP REQUEST message,and/or via any other IE and/or message.

In some demonstrative embodiments, MeNB 106 may be configured to sendthe offload information to SeNB 102, e.g., via X2 connection 108, and/orto SeNB 104, e.g., via X2 connection 109. For example, MeNB 106 may beconfigured to send the offload information to SeNB 102 and/or SeNB 104via an enhanced [X2-AP] SENB ADDITION REQUEST message, and/or any othermessage.

In some demonstrative embodiments, MeNB 106 may be configured to move anSCG bearer to SeNB 102 and/or to move an SCG bearer to SeNB 104, forexample, according to a dual connectivity procedure, e.g., using a SENBADDITION REQUEST X2AP message, and/or any other message.

In some demonstrative embodiments, MeNB 106 may be configured to includein a SENB ADDITION REQUEST X2AP message corresponding to an SCG bearerof a SeNB an IE including an offload indication to indicate whether ornot SeNB is allowed to offload traffic of the SCG (“offloadable SCG”) tothe Internet 122, e.g., according to a SIPTO mechanism.

In some demonstrative embodiments, SeNB 102 may be configured toselectively offload uplink traffic belonging to an SCG bearer of SeNB102, for example, based on the offload indication, e.g., as may bereceived in the IE of the X2AP message corresponding to the SCG bearer.

In some demonstrative embodiments, SeNB 102 may be configured to offloadtraffic of an SCG bearer to the Internet 122, for example, via route134, using NAT gateway 192, e.g., as described below.

In some demonstrative embodiments, for example, if the offloadindication of the SCG bearer of SeNB 102 indicates that offloadingtraffic of the SCG bearer is allowed, SeNB 102 may send uplink trafficbelonging to the SCG bearer to the NAT gateway 192, and/or SeNB 102 mayreceive downlink traffic for the SCG bearer either from the NAT gateway192 or from S-GW 130, e.g., as described below.

In some demonstrative embodiments, the NAT gateway 192 may beimplemented as a gateway, e.g., a dedicated NAT gateway or as part ofany other gateway, between SeNB 102 and the Internet 122, e.g., asdescribed below with reference to FIG. 3.

In some demonstrative embodiments, the NAT gateway 192 may be collocatedwith, and/or implemented as part of, SeNB 102, e.g., as described belowwith reference to FIG. 4.

In some demonstrative embodiments, system 100 may include a NAT gateway(not shown in FIG. 1), which may be configured to intercept a packet ofthe SCG bearer of SeNB 102 over S1-U interface 126 between SeNB 102 andSGW 130, and to selectively offload the traffic of the SCG bearer toInternet 122, e.g., as described below with reference to FIG. 5.

Reference is made to FIG. 2, which schematically illustrates elements ofa node 200, in accordance with some demonstrative embodiments.

In some demonstrative embodiments, an eNB operating as a SeNB, e.g.,node 102 and/or node 104 (FIG. 1), may include one or more of theelements of node 200, e.g., as described below.

In some demonstrative embodiments, node 200 may include a cellulartransceiver (TRx) 202 configured to communicate over a cellularfrequency band, for example, a cellular frequency band of a SCG. Forexample, node 102, and/or node 104 (FIG. 1) may include a cellular TRx202.

In some demonstrative embodiments, cellular TRx 202 may include one ormore wireless transmitters, receivers and/or transceivers includingcircuitry and/or logic configured to send and/or receive wirelesscommunication signals, RF signals, frames, blocks, transmission streams,packets, messages, data items, and/or data.

In some demonstrative embodiments, cellular TRx 202 may includecircuitry, logic, modulation elements, demodulation elements,amplifiers, analog to digital and digital to analog converters, filters,and/or the like.

In some demonstrative embodiments, cellular TRx 202 may include amultiple input multiple output (MIMO) transmitters receivers system (notshown), including circuitry and/or logic configured to perform antennabeamforming methods, if desired. In other embodiments, cellular TRx 202may include any other transmitters and/or receivers.

In some demonstrative embodiments, cellular TRx 202 may include LTE,WCDMA and/or TD-SCDMA modulator and/or demodulator circuitry (not shown)configured to modulate and/or demodulate signals to be transmitted by,and/or signals received by, node 200.

In some demonstrative embodiments, cellular TRx 202 may include adecoder, e.g., a turbo decoder, and/or an encoder, e.g., a turboencoder, (not shown) including circuitry and/or logic for encodingand/or decoding data bits into data symbols, if desired. In somedemonstrative embodiments, cellular TRx 202 may include OFDM and/orSC-FDMA modulators and/or demodulators (not shown) configured tocommunicate OFDM signals over downlink (DL) channels, and/or SC-FDMAsignals over uplink (UL) channels.

In some demonstrative embodiments, cellular TRx may include, or may beassociated with, one or more antennas. In one example, cellular TRx maybe associated with at least two antennas, e.g., antennas 208 and 210. Inanother example, cellular TRx may be associated with one antenna or morethan two antennas.

In some demonstrative embodiments, antennas 208 and/or 210 may includeany type of antennas suitable for transmitting and/or receiving wirelesscommunication signals, blocks, frames, transmission streams, packets,messages and/or data. For example, antennas 208 and/or 210 may includeany suitable configuration, structure and/or arrangement of one or moreantenna elements, components, units, assemblies and/or arrays. Forexample, antennas 208 and/or 210 may include a phased array antenna, adipole antenna, a single element antenna, a set of switched beamantennas, and/or the like.

In some embodiments, antennas 208 and/or 210 may implement transmit andreceive functionalities using separate transmit and receive antennaelements. In some embodiments, antennas 208 and/or 210 may implementtransmit and receive functionalities using common and/or integratedtransmit/receive elements.

In some demonstrative embodiments, node 200 may include an offloadingcontroller 240 to control one or more offloading functionalities of node200 and/or to control one or more operations and/or communicationsperformed by node 200, e.g., as described below. For example, node 102,and/or node 104 (FIG. 1) may include controller 240.

In some demonstrative embodiments, offloading controller 240 may includeor may be implemented using suitable circuitry and/or logic, e.g.,controller circuitry and/or logic, processor circuitry and/or logic,memory circuitry and/or logic, and/or any other circuitry and/or logic,which may be configured to perform at least part of the functionality ofoffloading controller 240. Additionally or alternatively, one or morefunctionalities of offloading controller 240 may be implemented bylogic, which may be executed by a machine and/or one or more processors,e.g., as described below.

In some demonstrative embodiments, node 200 may include a firstinterface 266 to communicate with a MeNB. For example, interface 266 mayinclude an X2 interface to communicate with a MeNB via an X2 connection.In one example, node 102 (FIG. 1) may include interface 266 configuredto communicate with MeNB 106 (FIG. 1) via X2 connection 108 (FIG. 1);and/or node 104 (FIG. 1) may include interface 266 configured tocommunicate with MeNB 106 (FIG. 1) via X2 connection 109 (FIG. 1).

In some demonstrative embodiments, node 200 may include a secondinterface 268 to communicate with a SGW. For example, interface 268 mayinclude an S1-U interface to communicate with a SGW via a S1-Uconnection. In one example, node 102 (FIG. 1) may include interface 268configured to communicate with SGW 130 (FIG. 1) via S1-U connection 126(FIG. 1); and/or node 104 (FIG. 1) may include interface 268 configuredto communicate with SGW 130 (FIG. 1) via S1-U connection 126 (FIG. 1).

In some demonstrative embodiments, cellular TRx 202 may be configured tocommunicate with a UE traffic of a SCG bearer according to a dualconnectivity scheme, and interface 268 may be configured to communicatetraffic of the SCG bearer with a SGW, e.g., as described below.

In one example, node 102 (FIG. 1) may include cellular TRx 202 tocommunicate with UE 119 (FIG. 1) traffic of a SCG bearer of SeNB-1according to a dual connectivity scheme, and node 102 (FIG. 1) mayinclude interface 268 configured to communicate the traffic of the SCGbearer with SGW 130 (FIG. 1) via the S1-U connection 126 (FIG. 1).

In another example, node 104 (FIG. 1) may include cellular TRx 202 tocommunicate with UE 119 (FIG. 1) traffic of a SCG bearer of SeNB-2according to a dual connectivity scheme, and node 104 (FIG. 1) mayinclude interface 268 configured to communicate the traffic of the SCGbearer with SGW 130 (FIG. 1) via the S1-U connection 126 (FIG. 1).

In some demonstrative embodiments, offloading controller 240 may beconfigured to offload the traffic of the SCG bearer to the Internet viaa NAT gateway, e.g., as described below. In one example, node 102(FIG. 1) may include offloading controller 240 configured to offloadtraffic of the SCG bearer of SeNB-1 to the Internet 122 (FIG. 1) via NATgateway 192 (FIG. 1); and/or node 104 (FIG. 1) may include offloadingcontroller 240 configured to offload traffic of the SCG bearer of SeNB-2to the Internet 122 (FIG. 1) via NAT gateway 192 (FIG. 1), e.g., asdescribed below.

In some demonstrative embodiments, node 200 may include a NAT gateway262, e.g., as described below with reference to FIG. 3. For example, NATgateway 262 may be configured to operate as, and/or perform thefunctionality of, NAT gateway 192 (FIG. 1).

In other embodiments, node 200 may include a NAT interface 264configured to communicate with the NAT gateway, for example NAT gateway129 (FIG. 1), e.g., as described below with reference to FIG. 4.

In some demonstrative embodiments, offloading controller 240 may beconfigured to process an uplink Internet Protocol (IP) packet receivedfrom a UE, via the SCG bearer according to the dual connectivity scheme.For example, cellular TRx 202 of node 102 (FIG. 1) may receive theuplink IP packet from UE 119 (FIG. 1), e.g., at SeNB 102 (FIG. 1), andoffloading controller 240 may process the received uplink IP packet.

In some demonstrative embodiments, offloading controller 240 may beconfigured to select, based on whether or not the SCG bearer is allowedto be offloaded, between routing the uplink IP packet to a SGW, androuting the uplink IP packet to the Internet via a NAT gateway. Forexample, based on whether or not the SCG bearer is allowed to beoffloaded, offloading controller 240 of node 02 (FIG. 1) may selectbetween routing the uplink IP packet to SGW 130 (FIG. 1), e.g., via S1-Uinterface 126 (FIG. 1), and routing the uplink IP packet to the Internet122 (FIG. 1) via NAT gateway 192 (FIG. 1), e.g., via route 134 (FIG. 1).

In some demonstrative embodiments, offloading controller 240 may beconfigured to select whether or not to offload the SCG bearer to theInternet based, for example, on an offload indication from a MeNB.

For example, node 102 (FIG. 1) may be configured to receive from MeNB106 (FIG. 1) an offload indication, e.g., via interface 266. The offloadindication may indicate, for example, whether or not the SCG bearer ofnode 102 (FIG. 1) is allowed to be offloaded. According to this example,offloading controller 240 of node 102 (FIG. 1) may be configured toselect whether or not to offload the SCG bearer to the Internet 122(FIG. 1), e.g., via route 134 (FIG. 1), for example, based on theoffload indication from MeNB 106 (FIG. 1).

In some demonstrative embodiments, at least part of the functionality ofoffloading controller 240 may be implemented by an integrated circuit,for example, a chip, e.g., a System on Chip (SoC). In one example, thechip or SoC may be configured to perform one or more operations and/orfunctionalities of cellular transceiver 202, interface 266, interface268, NAT gateway 262, and/or NAT interface 264. For example, the chip orSoC may include one or more elements of offloading controller 240,and/or one or more elements of cellular transceiver 202, interface 266,interface 268, NAT gateway 262, and/or NAT interface 264. In oneexample, offloading controller 240, cellular transceiver 202, interface266, interface 268 and NAT gateway 262 may be implemented as part of thechip or SoC. In another example, offloading controller 240, cellulartransceiver 202, interface 266, interface 268 and NAT interface 264 maybe implemented as part of the chip or SoC.

In other embodiments, offloading controller 240, cellular transceiver202, interface 266, interface 268 and/or NAT gateway 262 may beimplemented by one or more additional or alternative elements of node200.

In some demonstrative embodiments, node 200 may include, for example,one or more of a processor 220, a memory unit 222, and/or a storage unit224. In one example, one or more of processor, 220 memory 222 and/orstorage 224 may be implemented as one or more elements separate fromcellular transceiver 202, interface 266, interface 268, NAT gateway 262,and/or NAT interface 264. In another example, one or more of processor,220 memory 222 and/or storage 224 may be implemented as part of cellulartransceiver 202, interface 266, interface 268, NAT gateway 262, and/orNAT interface 264.

In some demonstrative embodiments, processor 220 includes, for example,a Central Processing Unit (CPU), a Digital Signal Processor (DSP), oneor more processor cores, a single-core processor, a dual-core processor,a multiple-core processor, a microprocessor, a host processor, acontroller, a plurality of processors or controllers, a chip, amicrochip, one or more circuits, circuitry, a logic unit, an IntegratedCircuit (IC), an Application-Specific IC (ASIC), or any other suitablemulti-purpose or specific processor or controller. Processor 220executes instructions, for example, of an Operating System (OS) of node200 and/or of one or more suitable applications.

In some demonstrative embodiments, memory unit 222 includes, forexample, a Random Access Memory (RAM), a Read Only Memory (ROM), aDynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, avolatile memory, a non-volatile memory, a cache memory, a buffer, ashort term memory unit, a long term memory unit, or other suitablememory units. Storage unit 224 includes, for example, a hard disk drive,a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVDdrive, or other suitable removable or non-removable storage units.Memory unit 222 and/or storage unit 224, for example, may store dataprocessed by node 200.

Reference is made to FIG. 3, which schematically illustrates a system300 including a NAT gateway 392 to offload traffic from at least oneSeNB, in accordance with some demonstrative embodiments. For example,NAT gateway 392 may be configured to operate as, and/or perform one ormore functionalities of NAT gateway 192 (FIG. 1).

In some demonstrative embodiments, NAT gateway 392 may be configured tocommunicate with the Internet 322, for example, using a NAT gateway IPaddress, which may include an externally routable network address, whichmay be configured to uniquely identify NAT gateway 392, e.g., on theInternet 322.

In some demonstrative embodiments, NAT gateway 392 may be connected toat least a first SeNB 302 and/or a second SeNB 304, for example, on abackhaul path between a local network 395 and the Internet 322. Forexample, SeNB 302 may operate as, and/or perform the functionality of,SeNB 102 (FIG. 1), SeNB 304 may operate as, and/or perform thefunctionality of, SeNB 104 (FIG. 1), and/or local network 395 mayperform the functionality of local network 195 (FIG. 1).

In some demonstrative embodiments, SeNB 302 and/or SeNB 304 may includeinterface 266 (FIG. 2) configured to communicate with a MeNB 306; acellular transceiver 202 (FIG. 2) to communicate with a UE 319 trafficof a SCG bearer according to a dual connectivity scheme; and aninterface 268 (FIG. 2) to communicate the traffic of the SCG bearer witha SGW 330, e.g., as described above.

In some demonstrative embodiments, SeNB 302 may be configured to forwarduplink IP packets of the SCG bearer of SeNB 302 to NAT gateway 392, forexample, if the SCG bearer is allowed to be offloaded; and/or SeNB 304may be configured to forward uplink IP packets of the SCG bearer of SeNB304 to NAT gateway 392, for example, if the SCG bearer is allowed to beoffloaded, e.g., as described below.

In some demonstrative embodiments, SeNB 302 and/or SeNB 304 may includeoffloading controller 240 (FIG. 2) to offload the traffic of the SCGbearer to the Internet 322 via NAT gateway 392, e.g., as describedbelow.

In some demonstrative embodiments, SeNB 302 and/or SeNB 304 may beconfigured to send uplink IP packets from SCG bearers marked asoffloadable to NAT gateway 329, for example, instead of sending theuplink IP packets to SGW 330, e.g., as described below.

In some demonstrative embodiments, SeNB 302 may be configured to receivean uplink IP from UE 319, e.g., via cellular transceiver 202 (FIG. 2),and offloading controller 240 (FIG. 2) of SeNB 302 may be configured tosend the uplink IP packet to NAT gateway 395 via a tunnel 393 betweenSeNB 302 and NAT gateway 392, for example, if the SCG bearer carryingthe uplink IP packet is allowed to be offloaded.

In some demonstrative embodiments, SeNB 304 may be configured to receivean uplink IP packet from UE 319, e.g., via cellular transceiver 202(FIG. 2), and offloading controller 240 (FIG. 2) of SeNB 304 may beconfigured to send the uplink IP packet to NAT gateway 395 via a tunnel394 between SeNB 304 and NAT gateway 392, for example, if the SCG bearercarrying the uplink IP packet is allowed to be offloaded.

In some demonstrative embodiments, tunnels 393 and/or 394 may bepre-established between SeNBs 302 and/or 304 and MeNB 306. In oneexample, tunnels 393 and/or 394 may include an IP tunnel, which mayutilize any IP tunneling protocol and/or scheme, and/or any othertunnel.

In some demonstrative embodiments, SeNB 302 may establish tunnel 393with NAT gateway 392, for example, using the NAT gateway IP address ofNAT gateway 392, which may be, for example, pre-configured at SeNB 302,e.g., using an Operations, administration and management (OAM)procedure; and/or SeNB 304 may establish tunnel 394 with NAT gateway392, for example, using the NAT gateway IP address of NAT gateway 392,which may be, for example, pre-configured at SeNB 304, e.g., using theOAM procedure.

In some demonstrative embodiments, NAT gateway 392 may be configured toperform NAT functionality, for example, to communicate traffic of theoffloaded SCG bearers with the Internet 322, e.g., directly, forexample, while bypassing the core network, e.g., as described below.

In some demonstrative embodiments, the uplink IP packet from UE 319 mayinclude IP address information corresponding to UE 319. The IP addressinformation, may include, for example, at least a source IP address, ora network prefix, and/or any other IP address information correspondingto UE 319, e.g., as described below.

In some demonstrative embodiments, NAT gateway 392 may be configured toconvert the IP address information included in the uplink IP packet intoan externally routable IP address, e.g., using the IP address assignedto NAT gateway 392, as described below.

In some demonstrative embodiments, NAT gateway 392 may be configured,for example, to change a source IP address, and, optionally, also a portnumber, of the uplink IP packet form UE 319, into the IP address of NATgateway 392, for example, if the uplink IP packet includes an IP Version4 (IPv4) packet.

In some demonstrative embodiments, NAT gateway 392 may be configured,for example, to change a source network prefix of the uplink IP packet,into the IP address of NAT gateway 392, for example, if the uplink IPpacket includes an IP Version 6 (IPv6) packet.

In some demonstrative embodiments, NAT gateway 392 may be configured tomap between a tunnel, from which an uplink IP packet is received, andthe IP address information included in the uplink IP packet. Forexample, NAT gateway 392 may be configured to map between tunnel 393 andIP address information included in an uplink IP packet received viatunnel 393.

In some demonstrative embodiments, NAT gateway 392 may maintain mappinginformation to map between a port number, and a source IP address and/ora network prefix of uplink IP packets received via tunnels 393 and/or394. Additionally or alternatively, NAT gateway 392 may be configured toimplement a stateless algorithmic mapping between local and externallyroutable prefixes, for example, in accordance with Internet EngineeringTask Force (IETF) Request for Comments (RFC) 6296 (ISSN 2070-1721, June2011) and/or any other mapping, e.g., if the uplink IP packets includeIPV6 packets.

In some demonstrative embodiments, NAT gateway 392 may maintain mappinginformation to associate between a tunnel through which uplink IPpackets were last received and a specific source IP address/port orsource IP prefix, e.g., which may be included in the uplink IP packets.

In some demonstrative embodiments, NAT gateway 392 may be configured touse the mapping information, for example, to route downlink packets, forexample, when UE 319 moves from one SeNB to another, e.g., from SeNB 302to SeNB 304.

In some demonstrative embodiments, NAT gateway 392 may be configured toforward the IP packets to the Internet 322, e.g., via the Internetconnection of local network 395.

In some demonstrative embodiments, NAT gateway 392 may be configured toroute downlink traffic received from Internet 322 via tunnels 393 and/or394, for example, based on the mapping information associated withtunnels 393 and 394, e.g., as described below.

In some demonstrative embodiments, NAT gateway 392 may be configured toreceive a downlink IP packet form the Internet 322 to be provided to UE319. The downlink IP address may include, for example, the IP address ofNAT gateway 392.

In some demonstrative embodiments, NAT gateway 392 may be configured toreplace the target IP address and port number of the downlink IP packetreceived from the Internet 322 with a target IP address and port addresscorresponding to UE 319, e.g., based on the mapping information, forexample, if the downlink IP packet is an IPv4 packet.

In some demonstrative embodiments, NAT gateway 392 may be configured toreplace the network prefix of the downlink IP packet received from theInternet 322 with a network prefix corresponding to UE 319, e.g., basedon the mapping information, for example, if the downlink IP packet is anIPv6 packet.

In some demonstrative embodiments, NAT gateway 392 may be configured todetermine whether to route the downlink IP packet via tunnel 393 ortunnel 394, e.g., based on the mapping information, to assign to thedownlink IP packet the IP address information corresponding to UE 319,and to send the downlink IP packet to SeNB 302 or SeNB 304, e.g., viatunnel 393 or via tunnel 394.

In some demonstrative embodiments, a system e.g., system 300, utilizinga NAT gateway, e.g., NAT gateway 392, configured to communicate with aplurality of SeNBs via a plurality of tunnels, may enable for example,to support IP prefix preservation, for example, in cases when UE 319 isto move from a first SeNB to a second SeNB, for example, when the firstand second SeNBs use a different globally routable set of IP prefixes.

FIG. 4 is a schematic illustration of a system 400 including a NATgateway 492 collocated with a SeNB 402 and a NAT gateway 491 collocatedwith a SeNB 404, in accordance with some demonstrative embodiments. Forexample, NAT gateway 492 and/or NAT gateway 491 may be configured tooperate as, and/or perform one or more functionalities of NAT gateway192 (FIG. 1). For example, SeNB 402 may operate as, and/or perform thefunctionality of, SeNB 102 (FIG. 1), and/or SeNB 404 may operate as,and/or perform the functionality of, SeNB 104 (FIG. 1).

In some demonstrative embodiments, NAT gateway 492 and/or NAT gateway491 may be connected to the Internet 422, for example, via a localnetwork 495, in which SeNB 402 and/or SeNB 404 may be deployed.

In some demonstrative embodiments, NAT gateway 492 may be configured tocommunicate with the Internet 422, e.g., via a direct access connection498, for example, using a NAT gateway IP address, which may include anexternally routable network address, which may be configured to uniquelyidentify NAT gateway 492, e.g., on the Internet 422.

In some demonstrative embodiments, NAT gateway 491 may be configured tocommunicate with the Internet 422, e.g., via a direct access connection497, for example, using a NAT gateway IP address, which may include anexternally routable network address, which may be configured to uniquelyidentify NAT gateway 491, e.g., on the Internet 422.

In some demonstrative embodiments, SeNB 402 may include NAT gateway 492,e.g., implemented as NAT gateway 262 (FIG. 2); and/or SeNB 404 mayinclude NAT gateway 491, e.g., implemented as NAT gateway 262 (FIG. 2).

In some demonstrative embodiments, implementing a NAT gateway, e.g., NATgateway 492 and/or NAT gateway 492, as part of a SeNB, e.g., SeNB 402and/or SeNB 404, may enable using the NAT gateway, e.g., even without apre-established tunnel between the SeNB and the NAT gateway.

In some demonstrative embodiments, SeNB 402 and/or SeNB 404 may includea cellular transceiver 202 (FIG. 2) to communicate with a UE 419 trafficof a SCG bearer according to a dual connectivity scheme; and aninterface 268 (FIG. 2) to communicate the traffic of the SCG bearer witha SGW 430, e.g., as described above.

In some demonstrative embodiments, SeNB 402 may include offloadingcontroller 240 (FIG. 2) configured to forward uplink IP packets of theSCG bearer of SeNB 402 to the Internet 422, e.g., via collocated NATgateway 492, for example, if the SCG bearer is allowed to be offloaded;and/or SeNB 404 may include offloading controller 240 (FIG. 2)configured to forward uplink IP packets of the SCG bearer of SeNB 404 tothe Internet 422, e.g., via collocated NAT gateway 491, for example, ifthe SCG bearer is allowed to be offloaded, e.g., as described below.

In some demonstrative embodiments, SeNB 402 and/or SeNB 404 may beconfigured to send uplink IP packets from SCG bearers marked asoffloadable to the Internet 422, for example, instead of sending theuplink IP packets to SGW 430, for example, encapsulated in generalpacket radio service (GPRS) Tunneling Protocol User Plane (GTP-U)packets.

In some demonstrative embodiments, the uplink IP packet from UE 419 mayinclude IP address information corresponding to UE 419. The IP addressinformation, may include, for example, at least a source IP address, ora network prefix, and/or any other IP address information correspondingto UE 419, e.g., as described below.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured to convert the IPaddress information included in the uplink IP packet into an externallyroutable IP address, e.g., using the IP address assigned to NAT gateway492, as described below.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured, for example, tochange a source IP address, and, optionally, also a port number, of theuplink IP packet form UE 419, into the IP address of NAT gateway 492,for example, if the uplink IP packet includes an IP Version 4 (IPv4)packet.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured, for example, tochange a source network prefix of the uplink IP packet, into the IPaddress of NAT gateway 492, for example, if the uplink IP packetincludes an IP Version 6 (IPv6) packet.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured to forward the uplinkIP packets to the Internet 422, e.g., via the Internet connection oflocal network 495.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured to receive a downlinkIP packet form the Internet 422 to be provided to UE 419. The downlinkIP address may include, for example, the IP address of NAT gateway 492.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured to replace the targetIP address and port number of the downlink IP packet received from theInternet 422 with a target IP address and port address corresponding toUE 419, for example, if the downlink IP packet is an IPv4 packet.

In some demonstrative embodiments, offloading controller 240 (FIG. 2) ofSeNB 402 and/or NAT gateway 492 may be configured to replace the networkprefix of the downlink IP packet received from the Internet 422 with anetwork prefix corresponding to UE 419, for example, if the downlink IPpacket is an IPv6 packet.

FIG. 5 is a schematic illustration of a system 500 including a NATgateway 592 to intercept and offload traffic of a SeNB 502 and/or a SeNB504, in accordance with some demonstrative embodiments. For example, NATgateway 592 may be configured to operate as, and/or perform one or morefunctionalities of NAT gateway 192 (FIG. 1). For example, SeNB 502 mayoperate as, and/or perform the functionality of, SeNB 102 (FIG. 1),and/or SeNB 504 may operate as, and/or perform the functionality of,SeNB 104 (FIG. 1).

In some demonstrative embodiments, NAT gateway 592 may be connected tothe Internet 522, for example, via a local network 595, in which SeNB502 and/or SeNB 504 may be deployed.

In some demonstrative embodiments, NAT gateway 592 may be configured tocommunicate with the Internet 522, e.g., via a direct access connection598, for example, using a NAT gateway IP address, which may include anexternally routable network address, which may be configured to uniquelyidentify NAT gateway 592, e.g., on the Internet 522.

In some demonstrative embodiments, NAT gateway 592 may be configured tointercept packets communicated from SeNB 402 and/or SeNB 404 to an SGW530 over a S1-U interface 526. For example, SGW 530 may perform thefunctionality of SGW 130 (FIG. 1) and/or S1-U interface 526 may performthe functionality of S1-U interface 126 (FIG. 1).

In some demonstrative embodiments, SeNB 402 and/or SeNB 404 may beconfigured to encapsulate uplink IP packets from SCG bearers, forexample, in a GTP-U header of GTP-U packets, and to forward theencapsulated uplink IP packets to SGW 530 on the S1-U interface 526.

In some demonstrative embodiments, NAT gateway 592 may reside on theS1-U interface 526, and may be configured to intercept all GTP-U packetscommunicated over S1-U interface 526.

In some demonstrative embodiments, NAT gateway 592 may be configured toinspect the headers of the intercepted GTP-U packets.

In some demonstrative embodiments, NAT gateway 592 may be configured toreceive offloading information from a MeNB 530, e.g., via a C-planeinterface 583 with the MeNB 530. The offloading information mayindicate, for example, which SCG bearers are offloadable to the Internet522, e.g., as described above.

In some demonstrative embodiments, NAT gateway 592 may be configured tooffload uplink IP packets of an SCG bearer to the Internet 522, forexample, if the SCG bearer is offloadable. For example, NAT gateway 592may be configured to decapsulate the GTP-U header of an interceptedGTP-U packet belonging to an offloadable SCG bearer, and to forward thedecapsulated IP packets to the Internet 522.

In some FIG. 6 is a schematic illustration of elements of a NAT gateway600, in accordance with some demonstrative embodiments. For example, NATgateway 600 may be configured to operate as, and/or perform one or morefunctionalities of NAT gateway 592 (FIG. 5).

In some demonstrative embodiments, NAT gateway 600 may include a networkinterface 602 to communicate with the Internet, e.g., to communicatewith the Internet 522 (FIG. 5) via connection 598 (FIG. 5).

In some demonstrative embodiments, NAT gateway 600 may include anS1-interface 604 including circuitry and/or logic configured tocommunicate over an S1-U interface, e.g., S1-U interface 526 (FIG. 5).

In some demonstrative embodiments, NAT gateway 600 may include a packetinterceptor 608 including circuitry and/or logic configured to interceptan uplink GTP-U packet of a SCG bearer over an interface between a SeNBand a SGW. For example, packet interceptor 608 may be configured tointercept an uplink GTP-U packet of a SCG bearer over interface 526(FIG. 5) between SGW 530 and SeNB 502 (FIG. 5) and/or SeNB 504, e.g., asdescribed above.

In some demonstrative embodiments, NAT gateway 600 may include a packetrouter 606 including circuitry and/or logic configured to determine iftraffic of the SCG bearer is allowed to be offloaded to the Internet,and if the traffic of the SCG bearer is allowed to be offloaded to theInternet, to decapsulate an uplink IP packet from the uplink GTP-Upacket and to forward the uplink IP packet to the Internet. For example,packet router 606 may be configured to determine if traffic of a SCGbearer of SeNB 502 (FIG. 5) is allowed to be offloaded to the Internet522 (FIG. 5), and if the traffic of the SCG bearer is allowed to beoffloaded to the Internet, to decapsulate an uplink IP packet from anuplink GTP-U packet intercepted over S1-U interface 530 (FIG. 5), and toforward the uplink IP packet to the Internet 522, e.g., via connection598 (FIG. 5).

In some demonstrative embodiments, packet router 606 may be configuredto determine if traffic of the SCG bearer is allowed to be offloaded tothe Internet based on an offload indication from a MeNB, e.g., MeNB 530(FIG. 5), as described above.

In some demonstrative embodiments, packet router 606 may be configuredto receive a downlink IP packet form the Internet, e.g., via networkinterface 603, to encapsulate the downlink IP packet in a downlink GTP-Upacket, and to forward the downlink GTP-U packet to the SeNB, e.g., viaS1-U interface 604.

In some demonstrative embodiments, NAT gateway 600 may include, forexample, a processor 612 and/or a memory 610. In one example, processor612 and/or memory 610 may be implemented as one or more elementsseparate from packet router 606, packet interceptor 608, networkinterface 602 and/or S1-U interface 604. In another example, processor612 and/or memory 610 may be implemented as part of packet router 606,packet interceptor 608, network interface 602 and/or S1-U interface 604.

In some demonstrative embodiments, processor 612 includes, for example,a Central Processing Unit (CPU), a Digital Signal Processor (DSP), oneor more processor cores, a single-core processor, a dual-core processor,a multiple-core processor, a microprocessor, a host processor, acontroller, a plurality of processors or controllers, a chip, amicrochip, one or more circuits, circuitry, a logic unit, an IntegratedCircuit (IC), an Application-Specific IC (ASIC), or any other suitablemulti-purpose or specific processor or controller. Processor 612executes instructions, for example, of an Operating System (OS) of NATgateway 600 and/or of one or more suitable applications.

In some demonstrative embodiments, memory 610 includes, for example, aRandom Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM(DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory,a non-volatile memory, a cache memory, a buffer, a short term memoryunit, a long term memory unit, or other suitable memory units. Memory610, for example, may store data processed by NAT gateway 600.

FIG. 7 is a schematic flow-chart illustration of a method of offloadingtraffic of a SCG, in accordance with some demonstrative embodiments. Insome embodiments, one or more of the operations of the method of FIG. 7may be performed by one or more elements of a system, e.g., system 100(FIG. 1), system 300 (FIG. 3), system 400 (FIG. 4), and/or system 500(FIG. 5); a node, e.g., node 102 (FIG. 1), node 104 (FIG. 1), and/ornode 200 (FIG. 2); a SeNB, e.g., SeNB 302 (FIG. 3), SeNB 304 (FIG. 3),SeNB 402 (FIG. 4), and/or SeNB 404 (FIG. 4); a NAT gateway, e.g., NATgateway 192 (FIG. 1), NAT gateway 262 (FIG. 2), NAT gateway 392 (FIG.3), NAT gateway 492 (FIG. 4), NAT gateway 491 (FIG. 4), NAT gateway 592(FIG. 5), and/or NAT gateway 600 (FIG. 6); an offloading controller,e.g., offloading controller 240 (FIG. 2); and/or a packet router, e.g.,packet router 606 (FIG. 6).

As indicated at block 702, the method may include identifying a SCGbearer that is offloadable to the Internet via a NAT gateway, based onoffloading information received from a MeNB.

As indicated at block 704, the method may include identifying the SCGbearer that is offloadable to the Internet at a SeNB in control of theSCG bearer. For example, SeNB 102 (FIG. 1) may be configured to identifya SCG bearer controller by SeNB 102 (FIG. 1) that is offloadable to theInternet via NAT gateway 192 (FIG. 1), e.g., as described above.

As indicated at block 706, the method may include identifying the SCGbearer that is offloadable to the Internet at the NAT gateway. Forexample, NAT gateway 592 (FIG. 5) may be configured to identify a SCGbearer controller by SeNB 502 (FIG. 1) that is offloadable to theInternet via NAT gateway 592 (FIG. 1), e.g., as described above.

As indicated at block 708, the method may include offloading uplink IPpackets of the SCG bearer to the Internet via the NAT gateway, if theSCG bearer is indicated to be offloadable. In one example, SeNB 102(FIG. 1) may offload uplink IP packets of the SCG bearer controlled bySeNB 102 (FIG. 1) to the Internet via NAT gateway 192 (FIG. 1), e.g., asdescribed above. In another example, NAT gateway 592 (FIG. 5) mayoffload uplink IP packets of the SCG bearer controlled by SeNB 502 (FIG.5) to the Internet, e.g., as described above.

Reference is made to FIG. 8, which schematically illustrates a productof manufacture 800, in accordance with some demonstrative embodiments.Product 800 may include a non-transitory machine-readable storage medium802 to store logic 804, which may be used, for example, to perform atleast part of the functionality of a node, e.g., node 102 (FIG. 1), node104 (FIG. 1), and/or node 200 (FIG. 2); a SeNB, e.g., SeNB 302 (FIG. 3),SeNB 304 (FIG. 3), SeNB 402 (FIG. 4), and/or SeNB 404 (FIG. 4); a NATgateway, e.g., NAT gateway 192 (FIG. 1), NAT gateway 262 (FIG. 2), NATgateway 392 (FIG. 3), NAT gateway 492 (FIG. 4), NAT gateway 401 (FIG.4), NAT gateway 592 (FIG. 5), and/or NAT gateway 600 (FIG. 6); anoffloading controller, e.g., offloading controller 240 (FIG. 2); and/ora packet router, e.g., packet router 606 (FIG. 6); and/or to perform oneor more operations discussed above, e.g., including one or moreoperations discussed with reference to FIG. 7. The phrase“non-transitory machine-readable medium” is directed to include allcomputer-readable media, with the sole exception being a transitorypropagating signal.

In some demonstrative embodiments, product 800 and/or machine-readablestorage medium 802 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 802 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 804 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 804 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an Evolved Node B (eNB) configured to operate as aSecondary eNB (SeNB), the eNB comprising a first interface configured tocommunicate with a Master eNB (MeNB); a cellular transceiver configuredto communicate with a User Equipment (UE) traffic of a Secondary CellGroup (SCG) bearer according to a dual connectivity scheme; a secondinterface to communicate the traffic of the SCG bearer with a ServingGateway (SGW); and an offloading controller configured to offload thetraffic of the SCG bearer to the Internet via a Network AddressTranslation (NAT) gateway.

Example 2 includes the subject matter of Example 1, and optionally,wherein the offloading controller is configured to select whether or notto offload the SCG bearer to the Internet based on an offload indicationreceived from the MeNB, the offload indication to indicate whether ornot the SCG bearer is allowed to be offloaded.

Example 3 includes the subject matter of Example 1 or 2, and optionally,wherein the cellular transceiver is to receive from the UE an uplinkInternet Protocol (IP) packet, the offloading controller to send theuplink IP packet to the NAT gateway via a tunnel between the eNB and theNAT gateway.

Example 4 includes the subject matter of Example 1 or 2, and optionally,comprising the NAT gateway.

Example 5 includes the subject matter of Example 4, and optionally,wherein the cellular transceiver is to receive from the UE an uplinkInternet Protocol (IP) packet comprising IP address informationcorresponding to the UE, the NAT gateway is configured to convert the IPaddress information into an IP address assigned to the NAT gateway.

Example 6 includes the subject matter of Example 5, and optionally,wherein the NAT gateway is to receive a downlink Internet Protocol (IP)packet form the Internet, the NAT gateway is configured to assign to thedownlink IP packet the IP address information corresponding to the UE.

Example 7 includes the subject matter of Example 5 or 6, and optionally,wherein the IP address information corresponding to the UE comprises asource IP address, or a network prefix.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, comprising one or more antennas, a memory and a processor.

Example 9 includes a Network Address Translation (NAT) gatewaycomprising a network interface to communicate with the Internet; apacket interceptor to intercept an uplink general packet radio service(GPRS) Tunneling Protocol User Plane (GTP-U) packet of a Secondary CellGroup (SCG) bearer over an interface between a Secondary evolved Node B(SeNB) and a Serving Gateway (SGW); and a packet router to determine iftraffic of the SCG bearer is allowed to be offloaded to the Internet,and if the traffic of the SCG bearer is allowed to be offloaded to theInternet, to decapsulate an uplink Internet Protocol (IP) packet fromthe uplink GTP-U packet and to forward the uplink IP packet to theInternet.

Example 10 includes the subject matter of Example 9, and optionally,wherein the packet router is configured to determine if traffic of theSCG bearer is allowed to be offloaded to the Internet based on anoffload indication from a Master evolved Node B (MeNB).

Example 11 includes the subject matter of Example 9 or 10, andoptionally, wherein the network interface is to receive a downlinkInternet Protocol (IP) packet form the Internet, the packet router isconfigured to encapsulate the downlink IP packet in a downlink GTP-Upacket, and to forward the downlink GTP-U packet to the SeNB.

Example 12 includes the subject matter of any one of Examples 9-11, andoptionally, wherein the packet interceptor is to intercept the uplinkGTP-U packet over an S1-U interface.

Example 13 includes the subject matter of any one of Examples 9-12, andoptionally, comprising a memory and a processor.

Example 14 includes an Evolved Node B (eNB) configured to operate as aSecondary eNB (SeNB), the eNB comprising a cellular transceiverconfigured to receive an uplink Internet Protocol (IP) packet from aUser Equipment (UE) via a Secondary Cell Group (SCG) bearer according toa dual connectivity scheme; and a controller configured to, based onwhether or not the SCG bearer is allowed to be offloaded, select betweenrouting the uplink IP packet to a Serving Gateway (SGW), and routing theuplink IP packet to the Internet via a Network Address Translation (NAT)gateway.

Example 15 includes the subject matter of Example 14, and optionally,wherein the controller is configured to determine if traffic of the SCGbearer is allowed to be offloaded to the Internet based on an offloadindication from a Master evolved Node B (MeNB).

Example 16 includes the subject matter of Example 14 or 15, andoptionally, wherein the controller is configured to route the uplink IPpacket to the NAT gateway via a tunnel between the SeNB and the NATgateway.

Example 17 includes the subject matter of Example 14 or 15, andoptionally, comprising the NAT gateway.

Example 18 includes the subject matter of Example 17, and optionally,wherein the uplink IP packet comprises IP address informationcorresponding to the UE, the controller is configured to convert the IPaddress information into an IP address assigned to the NAT.

Example 19 includes the subject matter of Example 18, and optionally,wherein the controller is configured to, upon receipt of a downlinkInternet Protocol (IP) packet form the Internet, assign to the downlinkIP packet the IP address information corresponding to the UE.

Example 20 includes the subject matter of Example 18 or 19, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Example 21 includes the subject matter of any one of Examples 14-20, andoptionally, comprising one or more antennas, a memory and a processor.

Example 22 includes an apparatus comprising circuitry configured tocause a Secondary Evolved Node B (SeNB), which is to communicate with aMaster eNB (MeNB), to communicate with a User Equipment (UE) traffic ofa Secondary Cell Group (SCG) bearer according to a dual connectivityscheme; communicate the traffic of the SCG bearer with a Serving Gateway(SGW); and offload the traffic of the SCG bearer to the Internet via aNetwork Address Translation (NAT) gateway.

Example 23 includes the subject matter of Example 22, and optionally,wherein the apparatus is configured to cause the SeNB to select whetheror not to offload the SCG bearer to the Internet based on an offloadindication received from the MeNB, the offload indication to indicatewhether or not the SCG bearer is allowed to be offloaded.

Example 24 includes the subject matter of Example 22 or 23, andoptionally, wherein the apparatus is configured to cause the SeNB tosend to the NAT gateway via a tunnel between the eNB and the NAT gatewayan uplink Internet Protocol (IP) packet received from the UE.

Example 25 includes the subject matter of Example 22 or 23, andoptionally, wherein the apparatus is configured to cause the SeNB tooperate as the NAT gateway.

Example 26 includes the subject matter of Example 25, and optionally,wherein the apparatus is configured to cause the NAT gateway to processan uplink Internet Protocol (IP) packet from the UE comprising IPaddress information corresponding to the UE, and to convert the IPaddress information into an IP address assigned to the NAT gateway.

Example 27 includes the subject matter of Example 26, and optionally,wherein the apparatus is configured to cause the NAT gateway to processa downlink Internet Protocol (IP) packet form the Internet, and toassign to the downlink IP packet the IP address informationcorresponding to the UE.

Example 28 includes the subject matter of Example 26 or 27, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Example 29 includes the subject matter of any one of Examples 22-28, andoptionally, comprising one or more antennas, a memory and a processor.

Example 30 includes an apparatus comprising circuitry configured tocause a Network Address Translation (NAT) gateway to intercept an uplinkgeneral packet radio service (GPRS) Tunneling Protocol User Plane(GTP-U) packet of a Secondary Cell Group (SCG) bearer over an interfacebetween a Secondary evolved Node B (SeNB) and a Serving Gateway (SGW);determine if traffic of the SCG bearer is allowed to be offloaded to theInternet; and if the traffic of the SCG bearer is allowed to beoffloaded to the Internet, decapsulate an uplink Internet Protocol (IP)packet from the uplink GTP-U packet and forward the uplink IP packet tothe Internet.

Example 31 includes the subject matter of Example 30, and optionally,wherein the apparatus is configured to cause the NAT gateway todetermine if traffic of the SCG bearer is allowed to be offloaded to theInternet based on an offload indication from a Master evolved Node B(MeNB).

Example 32 includes the subject matter of Example 30 or 31, andoptionally, wherein the apparatus is configured to cause the NAT gatewayto process a downlink Internet Protocol (IP) packet form the Internet,to encapsulate the downlink IP packet in a downlink GTP-U packet, and toforward the downlink GTP-U packet to the SeNB.

Example 33 includes the subject matter of any one of Examples 30-32, andoptionally, wherein the apparatus is configured to cause the NAT gatewayto intercept the uplink GTP-U packet over an S1-U interface.

Example 34 includes the subject matter of any one of Examples 30-33, andoptionally, comprising a memory and a processor.

Example 35 includes an apparatus comprising circuitry configured tocause a Secondary Evolved Node B (SeNB) to process an uplink InternetProtocol (IP) packet received from a User Equipment (UE) via a SecondaryCell Group (SCG) bearer according to a dual connectivity scheme; andbased on whether or not the SCG bearer is allowed to be offloaded,select between routing the uplink IP packet to a Serving Gateway (SGW),and routing the uplink IP packet to the Internet via a Network AddressTranslation (NAT) gateway.

Example 36 includes the subject matter of Example 35, and optionally,wherein the apparatus is configured to cause the SeNB to determine iftraffic of the SCG bearer is allowed to be offloaded to the Internetbased on an offload indication from a Master evolved Node B (MeNB).

Example 37 includes the subject matter of Example 35 or 36, andoptionally, wherein the apparatus is configured to cause the SeNB toroute the uplink IP packet to the NAT gateway via a tunnel between theSeNB and the NAT gateway.

Example 38 includes the subject matter of Example 35 or 36, andoptionally, wherein the apparatus is configured to cause the SeNB tooperate as the NAT gateway.

Example 39 includes the subject matter of Example 38, and optionally,wherein the uplink IP packet from the UE comprises IP addressinformation corresponding to the UE, the apparatus configured to causethe NAT gateway to convert the IP address information into an IP addressassigned to the NAT.

Example 40 includes the subject matter of Example 39, and optionally,wherein the apparatus is configured to cause the NAT gateway to assignthe IP address information corresponding to the UE to a downlinkInternet Protocol (IP) packet form the Internet.

Example 41 includes the subject matter of Example 39 or 40, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Example 42 includes the subject matter of any one of Examples 35-41, andoptionally, comprising one or more antennas, a memory and a processor.

Example 43 includes a method to be performed by a Secondary Evolved NodeB (SeNB), which is to communicate with a Master eNB (MeNB), the methodcomprising communicating with a User Equipment (UE) traffic of aSecondary Cell Group (SCG) bearer according to a dual connectivityscheme; communicating the traffic of the SCG bearer with a ServingGateway (SGW); and offloading the traffic of the SCG bearer to theInternet via a Network Address Translation (NAT) gateway.

Example 44 includes the subject matter of Example 43, and optionally,comprising selecting whether or not to offload the SCG bearer to theInternet based on an offload indication received from the MeNB, theoffload indication to indicate whether or not the SCG bearer is allowedto be offloaded.

Example 45 includes the subject matter of Example 43 or 44, andoptionally, comprising sending to the NAT gateway via a tunnel betweenthe eNB and the NAT gateway an uplink Internet Protocol (IP) packetreceived from the UE.

Example 46 includes the subject matter of Example 43 or 44, andoptionally, comprising processing an uplink Internet Protocol (IP)packet from the UE comprising IP address information corresponding tothe UE, and converting the IP address information into an IP addressassigned to the NAT gateway.

Example 47 includes the subject matter of Example 46, and optionally,comprising processing a downlink Internet Protocol (IP) packet form theInternet, and assigning to the downlink IP packet the IP addressinformation corresponding to the UE.

Example 48 includes the subject matter of 46 or 47, and optionally,wherein the IP address information corresponding to the UE comprises asource IP address, or a network prefix.

Example 49 includes a method to be performed by a Network AddressTranslation (NAT) gateway, the method comprising intercepting an uplinkgeneral packet radio service (GPRS) Tunneling Protocol User Plane(GTP-U) packet of a Secondary Cell Group (SCG) bearer over an interfacebetween a Secondary evolved Node B (SeNB) and a Serving Gateway (SGW);determining if traffic of the SCG bearer is allowed to be offloaded tothe Internet; and if the traffic of the SCG bearer is allowed to beoffloaded to the Internet, decapsulating an uplink Internet Protocol(IP) packet from the uplink GTP-U packet and forwarding the uplink IPpacket to the Internet.

Example 50 includes the subject matter of Example 49, and optionally,comprising determining if traffic of the SCG bearer is allowed to beoffloaded to the Internet based on an offload indication from a Masterevolved Node B (MeNB).

Example 51 includes the subject matter of Example 49 or 50, andoptionally, comprising processing a downlink Internet Protocol (IP)packet form the Internet, encapsulating the downlink IP packet in adownlink GTP-U packet, and forwarding the downlink GTP-U packet to theSeNB.

Example 52 includes the subject matter of any one of Examples 49-51, andoptionally, comprising intercepting the uplink GTP-U packet over an S1-Uinterface.

Example 53 includes a method to be performed at a Secondary Evolved NodeB (SeNB), the method comprising processing an uplink Internet Protocol(IP) packet received from a User Equipment (UE) via a Secondary CellGroup (SCG) bearer according to a dual connectivity scheme; and based onwhether or not the SCG bearer is allowed to be offloaded, selectingbetween routing the uplink IP packet to a Serving Gateway (SGW), androuting the uplink IP packet to the Internet via a Network AddressTranslation (NAT) gateway.

Example 54 includes the subject matter of Example 53, and optionally,comprising determining if traffic of the SCG bearer is allowed to beoffloaded to the Internet based on an offload indication from a Masterevolved Node B (MeNB).

Example 55 includes the subject matter of Example 53 or 54, andoptionally, comprising routing the uplink IP packet to the NAT gatewayvia a tunnel between the SeNB and the NAT gateway.

Example 56 includes the subject matter of Example 53 or 54, andoptionally, wherein the uplink IP packet from the UE comprises IPaddress information corresponding to the UE, the method comprisingconverting the IP address information into an IP address assigned to theNAT.

Example 57 includes the subject matter of Example 56, and optionally,comprising assigning the IP address information corresponding to the UEto a downlink Internet Protocol (IP) packet form the Internet.

Example 58 includes the subject matter of Example 56 or 57, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Example 59 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a Secondary Evolved Node B (SeNB),which is to communicate with a Master eNB (MeNB), the operationscomprising communicating with a User Equipment (UE) traffic of aSecondary Cell Group (SCG) bearer according to a dual connectivityscheme; communicating the traffic of the SCG bearer with a ServingGateway (SGW); and offloading the traffic of the SCG bearer to theInternet via a Network Address Translation (NAT) gateway.

Example 60 includes the subject matter of Example 59, and optionally,wherein the operations comprise selecting whether or not to offload theSCG bearer to the Internet based on an offload indication received fromthe MeNB, the offload indication to indicate whether or not the SCGbearer is allowed to be offloaded.

Example 61 includes the subject matter of Example 59 or 60, andoptionally, wherein the operations comprise sending to the NAT gatewayvia a tunnel between the eNB and the NAT gateway an uplink InternetProtocol (IP) packet received from the UE.

Example 62 includes the subject matter of Example 59 or 60, andoptionally, wherein the operations comprise processing an uplinkInternet Protocol (IP) packet from the UE comprising IP addressinformation corresponding to the UE, and converting the IP addressinformation into an IP address assigned to the NAT gateway.

Example 63 includes the subject matter of Example 62, and optionally,wherein the operations comprise processing a downlink Internet Protocol(IP) packet form the Internet, and assigning to the downlink IP packetthe IP address information corresponding to the UE.

Example 64 includes the subject matter of 62 or 63, and optionally,wherein the IP address information corresponding to the UE comprises asource IP address, or a network prefix.

Example 65 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a Network Address Translation (NAT)gateway, the operations comprising intercepting an uplink general packetradio service (GPRS) Tunneling Protocol User Plane (GTP-U) packet of aSecondary Cell Group (SCG) bearer over an interface between a Secondaryevolved Node B (SeNB) and a Serving Gateway (SGW); determining iftraffic of the SCG bearer is allowed to be offloaded to the Internet;and if the traffic of the SCG bearer is allowed to be offloaded to theInternet, decapsulating an uplink Internet Protocol (IP) packet from theuplink GTP-U packet and forwarding the uplink IP packet to the Internet.

Example 66 includes the subject matter of Example 65, and optionally,wherein the operations comprise determining if traffic of the SCG beareris allowed to be offloaded to the Internet based on an offloadindication from a Master evolved Node B (MeNB).

Example 67 includes the subject matter of Example 65 or 66, andoptionally, wherein the operations comprise processing a downlinkInternet Protocol (IP) packet form the Internet, encapsulating thedownlink IP packet in a downlink GTP-U packet, and forwarding thedownlink GTP-U packet to the SeNB.

Example 68 includes the subject matter of any one of Examples 65-67, andoptionally, wherein the operations comprise intercepting the uplinkGTP-U packet over an S1-U interface.

Example 69 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a Secondary Evolved Node B (SeNB),the operations comprising processing an uplink Internet Protocol (IP)packet received from a User Equipment (UE) via a Secondary Cell Group(SCG) bearer according to a dual connectivity scheme; and based onwhether or not the SCG bearer is allowed to be offloaded, selectingbetween routing the uplink IP packet to a Serving Gateway (SGW), androuting the uplink IP packet to the Internet via a Network AddressTranslation (NAT) gateway.

Example 70 includes the subject matter of Example 69, and optionally,comprising determining if traffic of the SCG bearer is allowed to beoffloaded to the Internet based on an offload indication from a Masterevolved Node B (MeNB).

Example 71 includes the subject matter of Example 69 or 70, andoptionally, wherein the operations comprise routing the uplink IP packetto the NAT gateway via a tunnel between the SeNB and the NAT gateway.

Example 72 includes the subject matter of Example 69 or 70, andoptionally, wherein the uplink IP packet from the UE comprises IPaddress information corresponding to the UE, the operations comprisingconverting the IP address information into an IP address assigned to theNAT.

Example 73 includes the subject matter of Example 72, and optionally,wherein the operations comprise assigning the IP address informationcorresponding to the UE to a downlink Internet Protocol (IP) packet formthe Internet.

Example 74 includes the subject matter of Example 72 or 73, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Example 75 includes an apparatus to perform one or more operations at aSecondary Evolved Node B (SeNB), which is to communicate with a MastereNB (MeNB), the apparatus comprising means for communicating with a UserEquipment (UE) traffic of a Secondary Cell Group (SCG) bearer accordingto a dual connectivity scheme; means for communicating the traffic ofthe SCG bearer with a Serving Gateway (SGW); and means for offloadingthe traffic of the SCG bearer to the Internet via a Network AddressTranslation (NAT) gateway.

Example 76 includes the subject matter of Example 75, and optionally,comprising means for selecting whether or not to offload the SCG bearerto the Internet based on an offload indication received from the MeNB,the offload indication to indicate whether or not the SCG bearer isallowed to be offloaded.

Example 77 includes the subject matter of Example 75 or 76, andoptionally, comprising means for sending to the NAT gateway via a tunnelbetween the eNB and the NAT gateway an uplink Internet Protocol (IP)packet received from the UE.

Example 78 includes the subject matter of Example 75 or 76, andoptionally, comprising means for operating as the NAT gateway.

Example 79 includes the subject matter of Example 78, and optionally,comprising means for processing an uplink Internet Protocol (IP) packetfrom the UE comprising IP address information corresponding to the UE,and converting the IP address information into an IP address assigned tothe NAT gateway.

Example 80 includes the subject matter of Example 79, and optionally,comprising means for processing a downlink Internet Protocol (IP) packetform the Internet, and assigning to the downlink IP packet the IPaddress information corresponding to the UE.

Example 81 includes the subject matter of 79 or 80, and optionally,wherein the IP address information corresponding to the UE comprises asource IP address, or a network prefix.

Example 82 includes an apparatus to perform one or more operations at aNetwork Address Translation (NAT) gateway, the apparatus comprisingmeans for intercepting an uplink general packet radio service (GPRS)Tunneling Protocol User Plane (GTP-U) packet of a Secondary Cell Group(SCG) bearer over an interface between a Secondary evolved Node B (SeNB)and a Serving Gateway (SGW); means for determining if traffic of the SCGbearer is allowed to be offloaded to the Internet; and means for, if thetraffic of the SCG bearer is allowed to be offloaded to the Internet,decapsulating an uplink Internet Protocol (IP) packet from the uplinkGTP-U packet and forwarding the uplink IP packet to the Internet.

Example 83 includes the subject matter of Example 82, and optionally,comprising means for determining if traffic of the SCG bearer is allowedto be offloaded to the Internet based on an offload indication from aMaster evolved Node B (MeNB).

Example 84 includes the subject matter of Example 82 or 83, andoptionally, comprising means for processing a downlink Internet Protocol(IP) packet form the Internet, encapsulating the downlink IP packet in adownlink GTP-U packet, and forwarding the downlink GTP-U packet to theSeNB.

Example 85 includes the subject matter of any one of Examples 82-84, andoptionally, comprising means for intercepting the uplink GTP-U packetover an S1-U interface.

Example 86 includes an apparatus to perform one or more operations at aSecondary Evolved Node B (SeNB), the apparatus comprising means forprocessing an uplink Internet Protocol (IP) packet received from a UserEquipment (UE) via a Secondary Cell Group (SCG) bearer according to adual connectivity scheme; and means for, based on whether or not the SCGbearer is allowed to be offloaded, selecting between routing the uplinkIP packet to a Serving Gateway (SGW), and routing the uplink IP packetto the Internet via a Network Address Translation (NAT) gateway.

Example 87 includes the subject matter of Example 86, and optionally,comprising means for determining if traffic of the SCG bearer is allowedto be offloaded to the Internet based on an offload indication from aMaster evolved Node B (MeNB).

Example 88 includes the subject matter of Example 86 or 87, andoptionally, comprising means for routing the uplink IP packet to the NATgateway via a tunnel between the SeNB and the NAT gateway.

Example 89 includes the subject matter of Example 86 or 87, andoptionally, comprising means for performing operations of the NATgateway.

Example 90 includes the subject matter of Example 89, and optionally,wherein the uplink IP packet from the UE comprises IP addressinformation corresponding to the UE, the apparatus comprising means forconverting the IP address information into an IP address assigned to theNAT.

Example 91 includes the subject matter of Example 90, and optionally,comprising means for assigning the IP address information correspondingto the UE to a downlink Internet Protocol (IP) packet form the Internet.

Example 92 includes the subject matter of Example 90 or 91, andoptionally, wherein the IP address information corresponding to the UEcomprises a source IP address, or a network prefix.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

1.-25. (canceled)
 26. An Evolved Node B (eNB) configured to operate as aSecondary eNB (SeNB), the eNB comprising: a first interface configuredto communicate with a Master eNB (MeNB); a cellular transceiverconfigured to communicate with a User Equipment (UE) traffic of aSecondary Cell Group (SCG) bearer according to a dual connectivityscheme; a second interface to communicate the traffic of the SCG bearerwith a Serving Gateway (SGW); and an offloading controller configured tooffload the traffic of the SCG bearer to the Internet via a NetworkAddress Translation (NAT) gateway.
 27. The eNB of claim 26, wherein saidoffloading controller is configured to select whether or not to offloadthe SCG bearer to the Internet based on an offload indication receivedfrom the MeNB, the offload indication to indicate whether or not the SCGbearer is allowed to be offloaded.
 28. The eNB of claim 26, wherein thecellular transceiver is to receive from the UE an uplink InternetProtocol (IP) packet, the offloading controller to send the uplink IPpacket to the NAT gateway via a tunnel between the eNB and the NATgateway.
 29. The eNB of claim 26 comprising the NAT gateway.
 30. The eNBof claim 29, wherein the cellular transceiver is to receive from the UEan uplink Internet Protocol (IP) packet comprising IP addressinformation corresponding to the UE, the NAT gateway is configured toconvert the IP address information into an IP address assigned to theNAT gateway.
 31. The eNB of claim 30, wherein the NAT gateway is toreceive a downlink Internet Protocol (IP) packet form the Internet, theNAT gateway is configured to assign to the downlink IP packet the IPaddress information corresponding to the UE.
 32. The eNB of claim 30,wherein the IP address information corresponding to the UE comprises asource IP address, or a network prefix.
 33. The eNB of claim 26comprising one or more antennas, a memory and a processor.
 34. A NetworkAddress Translation (NAT) gateway comprising: a network interface tocommunicate with the Internet; a packet interceptor to intercept anuplink general packet radio service (GPRS) Tunneling Protocol User Plane(GTP-U) packet of a Secondary Cell Group (SCG) bearer over an interfacebetween a Secondary evolved Node B (SeNB) and a Serving Gateway (SGW);and a packet router to determine if traffic of the SCG bearer is allowedto be offloaded to the Internet, and if the traffic of the SCG bearer isallowed to be offloaded to the Internet, to decapsulate an uplinkInternet Protocol (IP) packet from the uplink GTP-U packet and toforward the uplink IP packet to the Internet.
 35. The NAT gateway ofclaim 34, wherein said packet router is configured to determine iftraffic of the SCG bearer is allowed to be offloaded to the Internetbased on an offload indication from a Master evolved Node B (MeNB). 36.The NAT gateway of claim 34, wherein said network interface is toreceive a downlink Internet Protocol (IP) packet form the Internet, thepacket router is configured to encapsulate the downlink IP packet in adownlink GTP-U packet, and to forward the downlink GTP-U packet to theSeNB.
 37. The NAT gateway of claim 34, wherein said packet interceptoris to intercept said uplink GTP-U packet over an S1-U interface.
 38. TheNAT gateway of claim 34 comprising a memory and a processor.
 39. Anapparatus comprising circuitry configured to cause a Secondary EvolvedNode B (SeNB) to: process an uplink Internet Protocol (IP) packetreceived from a User Equipment (UE) via a Secondary Cell Group (SCG)bearer according to a dual connectivity scheme; and based on whether ornot the SCG bearer is allowed to be offloaded, select between routingthe uplink IP packet to a Serving Gateway (SGW), and routing the uplinkIP packet to the Internet via a Network Address Translation (NAT)gateway.
 40. The apparatus of claim 39 configured to cause the SeNB todetermine if traffic of the SCG bearer is allowed to be offloaded to theInternet based on an offload indication from a Master evolved Node B(MeNB).
 41. The apparatus of claim 39 configured to cause the SeNB toroute the uplink IP packet to the NAT gateway via a tunnel between theSeNB and the NAT gateway.
 42. The apparatus of claim 39 configured tocause the SeNB to operate as the NAT gateway.
 43. The apparatus of claim42, wherein the uplink IP packet from the UE comprises IP addressinformation corresponding to the UE, the apparatus configured to causethe NAT gateway to convert the IP address information into an IP addressassigned to the NAT.
 44. The apparatus of claim 43 configured to causethe NAT gateway to assign the IP address information corresponding tothe UE to a downlink Internet Protocol (IP) packet form the Internet.45. A product comprising one or more tangible computer-readablenon-transitory storage media comprising computer-executable instructionsoperable to, when executed by at least one computer processor, enablethe at least one computer processor to implement one or more operationsat a Secondary Evolved Node B (SeNB), which is to communicate with aMaster eNB (MeNB), the operations comprising: communicating with a UserEquipment (UE) traffic of a Secondary Cell Group (SCG) bearer accordingto a dual connectivity scheme; communicating the traffic of the SCGbearer with a Serving Gateway (SGW); and offloading the traffic of theSCG bearer to the Internet via a Network Address Translation (NAT)gateway.
 46. The product of claim 45, wherein the operations compriseselecting whether or not to offload the SCG bearer to the Internet basedon an offload indication received from the MeNB, the offload indicationto indicate whether or not the SCG bearer is allowed to be offloaded.47. The product of claim 45, wherein the operations comprise sending tothe NAT gateway via a tunnel between the eNB and the NAT gateway anuplink Internet Protocol (IP) packet received from the UE.
 48. Theproduct of claim 45, wherein the operations comprise processing anuplink Internet Protocol (IP) packet from the UE comprising IP addressinformation corresponding to the UE, and converting the IP addressinformation into an IP address assigned to the NAT gateway.
 49. Theproduct of claim 48, wherein the operations comprise processing adownlink Internet Protocol (IP) packet form the Internet, and assigningto the downlink IP packet the IP address information corresponding tothe UE.
 50. The product of 48, wherein the IP address informationcorresponding to the UE comprises a source IP address, or a networkprefix.